Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1793

reference: 987-tree-1
name: 1793
tree-preservation-order: undefined
987-tpo-1
uprn
address-text
point: POINT (-0.974207 50.858419)
geometry: MULTIPOLYGON (((-0.974122 50.858410,-0.974125 50.858427,-0.974137 50.858442,-0.974156 50.858454,-0.974179 50.858462,-0.974206 50.858465,-0.974232 50.858462,-0.974256 50.858455,-0.974275 50.858443,-0.974287 50.858428,-0.974292 50.858412,-0.974288 50.858395,-0.974276 50.858380,-0.974258 50.858368,-0.974234 50.858360,-0.974208 50.858357,-0.974182 50.858359,-0.974158 50.858367,-0.974139 50.858379,-0.974126 50.858393,-0.974122 50.858410)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL